Crate aleph_bft_types

source ·
Expand description

Traits that need to be implemented by the user.

Structs§

  • Error resulting from multisignature being incomplete.
  • A pair consistsing of signable data and a NodeIndex.
  • Signable data together with a complete multisignature.
  • Node count. Right now it doubles as node weight in many places in the code, in the future we might need a new type for that.
  • The index of a node
  • A container keeping items indexed by NodeIndex.
  • Error type returned when a verification of a signature fails.
  • A correctly signed object of type T.
  • A pair consisting of an instance of the Signable trait and an (arbitrary) signature.

Enums§

  • Signable data together with a valid partial multisignature.
  • A recipient of a message, either a specific node or everyone.

Traits§

  • Data type that we want to order.
  • The source of data items that consensus should order.
  • The source of finalization of the units that consensus produces.
  • A hasher, used for creating identifiers for blocks or units.
  • Indicates that an implementor has been assigned some index.
  • Abstraction of the signing data and verifying signatures.
  • Extends Keychain with multisigning functionalities.
  • Network represents an interface for sending and receiving NetworkData.
  • A type to which signatures can be aggregated.
  • Data which can be signed.
  • The type used as a signature.
  • An abstraction for an execution engine for Rust’s asynchronous tasks.

Type Aliases§

  • An asynchronous round of the protocol.
  • The number of a session for which the consensus is run.
  • A set of signatures of a subset of nodes serving as a (partial) multisignature
  • A handle for waiting the task’s completion.